Cryptext x64 0.4a - CNG + file-format v1 RAM test
=================================================

1. Build with build.bat using FASM 1.73.x.
2. Start Cryptext64.exe.
3. Enter any non-empty password, physically or with the virtual keyboard.
4. Optional: click ↻ before/during virtual input.
5. Click OK.

Expected result:
  CNG-Krypto-Selbsttest + Dateiformat v1: OK

The run proves:
- SecureInput reaches PBKDF2-HMAC-SHA-256.
- AES-256-GCM encrypt/decrypt works through CNG.
- GCM rejects a modified tag.
- The frozen CT64FILE v1 header builder/validator agrees on the layout.
- Nonce index 0x01020304 is encoded big-endian after the 8-byte prefix.
- AAD uses exact header bytes followed by little-endian index and length.
- Encrypted-size calculation handles a multi-chunk example.
- Unknown v1 header flags are rejected.

No user file is opened, created, renamed, encrypted or deleted by 0.4a.

Interoperability fixtures:
- Cryptext-v1-test-vector.txt      full published values
- Cryptext-v1-test-vector.bin      complete 188-byte deterministic v1 file
- Cryptext-v1-test-plaintext.txt   expected 36-byte plaintext payload

Test-vector password:
  Test0815$#!

The vector uses 10,000 PBKDF2 iterations only so independent implementations
can verify it quickly. The reference writer default is 600,000 and is stored
per file.
